SPARKC-710: Update component versions #1367
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jacek-lewandowski
force-pushed
the
SPARKC-710
branch
7 times, most recently
from
6445bdf to
41ca19f
Compare
jacek-lewandowski
force-pushed
the
SPARKC-710
branch
from
3ca7f93 to
7320f6a
Compare
jtgrabowski
approved these changes
May 13, 2024
msmygit
reviewed
May 13, 2024
|
|
||
| // C* versions | ||
| val V4_0_0: Version = Version.parse("4.0.0") | ||
| val V5_0_0: Version = Version.parse("5.0-alpha1") |
There was a problem hiding this comment.
nit - should we use 5.0-beta1 here instead?
tarzanek
pushed a commit
to tarzanek/spark-scylladb-connector
that referenced
this pull request
Aug 28, 2024
Updated Cassandra driver version and Cassandra versions used for testing
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
How did the Spark Cassandra Connector Work or Not Work Before this Patch
Describe the problem, or state of the project that this patch fixes. Explain
why this is a problem if this isn't obvious.
Example:
"When I read from tables with 3 INTS I get a ThreeIntException(). This is a problem because I often want to read from a table with three integers."
General Design of the patch
How the fix is accomplished, were new parameters or classes added? Why did you
pursue this particular fix?
Example: "I removed the incorrect assertion which would throw the ThreeIntException. This exception was incorrectly added and the assertion is not actually needed."
Fixes: Put JIRA Reference HERE
How Has This Been Tested?
Almost all changes and especially bug fixes will require a test to be added to either the integration or Unit Tests. Any tests added will be automatically run on travis when the pull request is pushed to github. Be sure to run suites locally as well.
Checklist: